Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1609

reference
538-tree-1
name
1609
tree-preservation-order

undefined

538-tpo-1
uprn
address-text
point
POINT (-1.022894 50.884710)
geometry
MULTIPOLYGON (((-1.022837 50.884704,-1.022839 50.884715,-1.022847 50.884725,-1.022860 50.884733,-1.022875 50.884738,-1.022893 50.884740,-1.022911 50.884738,-1.022927 50.884734,-1.022939 50.884726,-1.022948 50.884716,-1.022951 50.884705,-1.022948 50.884693,-1.022940 50.884683,-1.022928 50.884675,-1.022912 50.884670,-1.022895 50.884668,-1.022877 50.884670,-1.022861 50.884675,-1.022848 50.884683,-1.022840 50.884693,-1.022837 50.884704)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL